Medway Council

Tree preservation zone

There is a problem

• 54 entries must have dates in YYYY-MM-DD format

entity: 19128684

• reference: M28-1998
• geometry: MULTIPOLYGON (((0.526938 51.344779,0.526914 51.344773,0.526906 51.344761,0.526913 51.344749,0.526931 51.344743,0.526947 51.344744,0.526963 51.344757,0.526960 51.344770,0.526938 51.344779)),((0.526894 51.344786,0.526876 51.344792,0.526851 51.344787,0.526843 51.344775,0.526850 51.344762,0.526868 51.344756,0.526892 51.344761,0.526901 51.344773,0.526894 51.344786)),((0.526941 51.344828,0.526919 51.344837,0.526895 51.344831,0.526887 51.344819,0.526894 51.344807,0.526912 51.344801,0.526928 51.344802,0.526944 51.344815,0.526941 51.344828)))
• point: POINT (0.526907 51.344784)
• entry-date: 2025-01-18
• start-date:

  start-date must be a real date

How to fix this issue

Your dataset is missing the start-date column.

The Tree preservation zone guidance explains how to fix the issue:

start-date

The date that the tree preservation order came into force, written in YYYY-MM-DD format.

Example: 1984-03-28

How to improve Medway Council’s data

1. Fix the errors indicated
2. Use the check service to make sure the data meets the standard
3. Publish the updated data on the endpoint URL